LOWK, missing aeronautical and topographic data

Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

Home
»
Discussion Forums
»
Charts and Aeronautical Data
»
LOWK, missing aeronautical and topographic data

LOWK, missing aeronautical and topographic data

Author	Message
pseudonym	pseudonym posted 10/22/2018 4:07:00 PM HOT Topic Details Share Topic
Group: Forum Members Posts: 50, Visits: 189	To illustrate the setting, please find below a) the Skydemon chart, b) the VFR approach chart, c) the IFR obstacle chart, d) a topographic map e) Jeppesen mobile flight deck of Klagenfurt and the immediate region north of the airport. Klagenfurt LOWK in Austria is situated at the south border of the alps in the "basin of Klagenfurt". The town is surrounded by hills and mountains of 1000ft to 1300ft agl. 1. There are two VFR approaches, from the north and the west. Both are equipped with VRP (E1 and E2 and N1,N2 and N3). 2. VFR approach is by sectors (see b)) with a maximum altitude of 3500ft 3. two small holdings at 3000ft (see b)) 4. directly north of the aerodrome are hills of 1000ft agl (see c), d), e)) Skydemon depicts only the VRP (1). The sectors (2) are missing, max. sector altitude is not shown, the holdings (3) and their altitude are not shown, the terrain (4) is not displayed. But it is the terrain that forces an atypical close and atypical high downwind for an international airport. All this gives the false impression using Skydemon of a free approach sector north while there are hills 1000ft agl. The mental picture provided by the Jeppesen chart is fundamentally different: in fact, the north sector is anything but free of obstacles. While I very much like Skydemon as my most convenient navigational tool, it is probably not suited for mountaineous areas. This is a pity and this post is a plea for a more comprehensive depiction of heights (at least in the vicinity of airports) and the inclusion of AIP data (for both, see eg. Jeppesen). Kindest regards a) Skydemon map b) VFR approach chart from the AIP c) obstacle chart ICAO type b from the AIP d) topographic chart 1:30000 from opentopomap.org e) Jeppesen Mobile Flite Deck
	Reply Like 5
Replies
pseudonym	pseudonym posted 10/26/2018 8:57:08 AM Post Details Share Post
Group: Forum Members Posts: 50, Visits: 189	+x pgroell - 10/26/2018 8:19:51 AM Hello, I'm not trying to take side in this little discussion but I'm interested as I'm not used to flying in mountainous areas and try to gain all means to get a better image of the terrain I'm flying to. One tool that I use in SD is the ability to color terrain, I usually set the projected flying height as the reference altitude it then shows in red all terrain only 500ft below me. For flying into an airfield like LOWK one could set the reference as 3000ft which will show in red all terrain 1000ft AAL, in orange all terrain 500ft AAL and yellow all terrain below 500ft AAL. (see picture) It is great as a planning tool, maybe less for flying as it clutters the screen a bit. I know it does not really answer your request but to me seems at least an interesting workaround. Yes, this could/should fill in the gap of missing elevation points. it is probably not suitable for the approach (fiddling around with preferences of your navigational tool while sinking from 8000ft asl to 2400ft asl (pattern alt). But one could use this as a supplemental obstacle chart while flight planning. I should include this in my workflow. The hills which triggered my post are between N3 and the runway. But even with your large scale you see the problem of VRP Sierra (recommended departure route) 1400ft aal, which means that scattered/broken 1300ft is not sufficient for that departure.
	Reply Like 4
pseudonym	pseudonym posted 10/26/2018 10:07:19 AM Post Details Share Post
Group: Forum Members Posts: 50, Visits: 189	+x pseudonym - 10/26/2018 8:57:08 AM +x pgroell - 10/26/2018 8:19:51 AM Hello, I'm not trying to take side in this little discussion but I'm interested as I'm not used to flying in mountainous areas and try to gain all means to get a better image of the terrain I'm flying to. One tool that I use in SD is the ability to color terrain, I usually set the projected flying height as the reference altitude it then shows in red all terrain only 500ft below me. For flying into an airfield like LOWK one could set the reference as 3000ft which will show in red all terrain 1000ft AAL, in orange all terrain 500ft AAL and yellow all terrain below 500ft AAL. (see picture) It is great as a planning tool, maybe less for flying as it clutters the screen a bit. I know it does not really answer your request but to me seems at least an interesting workaround. Yes, this could/should fill in the gap of missing elevation points. it is probably not suitable for the approach (fiddling around with preferences of your navigational tool while sinking from 8000ft asl to 2400ft asl (pattern alt). But one could use this as a supplemental obstacle chart while flight planning. I should include this in my workflow. The hills which triggered my post are between N3 and the runway. But even with your large scale you see the problem of VRP Sierra (recommended departure route) 1400ft aal, which means that scattered/broken 1300ft is not sufficient for that departure. I got it, finally. This is what I was basically looking for: the terrain warning wth a reference altitude of 2250ft (800ft AAL, typical traffic pattern altitude). The problems north of the "L" of LOWK south of N3 as well as VRP Sierra are clearly visible. I don't hav a good idea how to integrate this in flight as the flight level in the Alps may change, but for flight preparation it is fine. Thus, as Tim Dawson pointed out, the data are there, now they are visible. @TD: maybe you find a way to combine the cleanliness of the in-flight display of SD with the detail advantageous in some circumstances. I have no idea how to do this without adding even more features. I fear SD might become a little obese if every request results in another feature. Maybe having a switch (at the layers preferences) which facultatively displays the terrain and sets ref alt to 1000ft AAL if closer than 3NM from the aerodrome. @pgroell: My tablet is an Ipad Mini from 2014. Your screen resolution appears to be higher. What hardware do you use?
	Reply Like 5